Schema Extension Snapshot Registry view

Administration System Schema Extension Snapshot Registry Schema Extension Snapshot Registry view

The Schema Extension Snapshot Registry view lists the schema snapshots of all enabled items in the Modification Registry from which N4 directly applies the schema extensions at startup. This includes snapshots of:

• Currently applied schema extensions

• Future schema extensions to be applied at the next solo startup

• Previously applied schema extensions, possibly to be reused at rollback

A schema snapshot is a frozen definition of the schema at a particular point in time. N4 automatically generates a snapshot when you lock and approve schema extension modifications in the Schema Extension Modification Registry view (on page 1) (Actions Create Schema Snapshot). Only one snapshot can be directly applied to the system.

You can edit and delete schema snapshots in this view.

Once a snapshot has been applied to the database, you can no longer modify any of the dynamic flex fields or dynamic entity fields. If you need to make changes, for example to the length of a string-type field, you must first delete the field from the database and then re-apply the snapshot to the database, with the modified field.

In addition, you can use the Actions menu to:

• View Persistence Events (on page 1): Open the Persistence Systems Events view to keep track of what has been applied to the system.

• Reload Session Factory: Approve the snapshot to be applied at restart. See also Session Factory view.

This option performs a hot reload of the session factory. In production, a hot reload disrupts all processes for a few minutes. In addition, suspending the second level cache is not supported and can cause transaction failures on other nodes in a clustered system. A hot reload clears all second level cache contents, which can cause a temporary performance bump. Therefore, a hot reload is only recommended for testing.

Schema Extension Snapshot Registry Columns